Connectivity scheduler for nb-iot devices

ABSTRACT

A method performed by one or more network nodes of a wireless telecommunications network to schedule intermittent connectivity of multiple narrowband Internet-of-Things (NB-IoT) devices with the network. The network node(s) can maintain a connectivity schedule that includes profiles for NB-IoT devices and cause the multiple NB-IoT devices to connect to the network in accordance with the schedule at different times based on priority levels associated with the NB-IoT devices. The network node(s) can adjust the connectivity schedule in response to detection of a condition of the network or the NB-IoT device.

BACKGROUND

Fifth generation (5G) technology aims to operationalize differentwireless technologies such as millimeter wave (mW) bands, along withLTE, WiFi, Bluetooth, and legacy cellular standards. 5G can supportapplications that have never been supported before in any wirelesstechnology, including augmented and virtual reality (AR/VR),internet-of-things (IoT), device-to-device (D2D) communication, machinetype communication (MTC), carrier aggregation (CA), dual connectivity(DC), relay nodes, autonomous cars, mission-critical applications,industry automation and control, etc.

5G will be readily used by billions of subscribers around the world thatwant access to voice-centric technology and rich multimediaapplications, video streaming, rich Internet browsing, chatting andvoice over legacy IP networks. In addition, 5G networks will need tosupport billions more Narrowband Internet of Things (NB-IoT) devices.NB-IoT technology is a low power, wide area network (LPWAN) radiotechnology standard developed by 3GPP to enable a wide range of devicesand services. NB-IoT devices have low-complexity, low power consumption,low data rates, use limited bandwidth, extended coverage, and lowhardware cost. Some NB-IoT devices have no mobility support.

NB-IoT devices can independently operate in licensed or unused bands ofa 5G network and/or by using specific resource blocks allocated by basestations for NB-IoT communications. NB-IoT technology has a coreprotocol stack and can perform operations that are defined by 3GPPspecifications. Examples of NB-IoT applications include smart metering(e.g., electricity, gas, water metering) for commercial services,intruder and fire alarms for homes and other properties for emergencyservices, and personal applications for measuring health parameters,tracking people, animals, or objects for non-commercial services. Otherexamples include smart city infrastructures such as smart lamps andconnected industrial applications such as welding machines or aircompressors.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present technology will be described and explainedthrough the use of the accompanying drawings.

FIG. 1 is a block diagram that illustrates a wireless communicationssystem.

FIG. 2 is a block diagram that illustrates an architecture of networkfunctions of a 5G network.

FIG. 3 is a flowchart that illustrates a method performed by one or morenetwork nodes to update a connectivity schedule for intermittentconnectivity between narrowband Internet-of-Things (NB-IoT) devices anda wireless telecommunications network.

FIG. 4 is a flowchart that illustrates a method performed by one or morenetwork nodes to configure a virtual integrated universal integratedcircuit card (UICC) that is integrated in an NB-IoT device of a wirelesstelecommunications network.

FIG. 5 is a flowchart that illustrates a method performed by one or morenetwork nodes to dynamically manage encryption keys of varyingencryption strengths for NB-IoT devices of a wireless telecommunicationsnetwork.

FIG. 6 is a block diagram that illustrates an example of a computingsystem in which at least some operations described herein can beimplemented.

Various features of the technologies described herein will become moreapparent to those skilled in the art from a study of the DetailedDescription in conjunction with the drawings. Embodiments areillustrated by way of example and not limitation in the drawings, inwhich like references may indicate similar elements. While the drawingsdepict various embodiments for the purpose of illustration, thoseskilled in the art will recognize that alternative embodiments may beemployed without departing from the principles of the technologies.Accordingly, while specific embodiments are shown in the drawings, thetechnology is amenable to various modifications.

DETAILED DESCRIPTION

The disclosed technologies relate to solving problems that arise fromhaving numerous internet-of-things devices, such as narrowbandinternet-of-things (NB-IoT) devices, on telecommunications networks(e.g., 5G networks). The NB-IoT devices have diverse capabilities andare generally designed as low-cost, low-power consumption devices thatconnect to a 5G network (“network”) to report sensor data.

An aspect of the technology includes a connectivity scheduler for NB-IoTdevices. A unified data management (UDM) function of a 5G networkmanages a connectivity schedule, which can be implemented as accesspolicies of a policy control function (PCF). The UDM stores a deviceprofile for each NB-IoT, which includes capability and serviceinformation. The capability or service information can be obtained froma session management function (SMF) or an IP multimedia subsystem (IMS)function. The device profiles are used to prioritize intermittentconnections based on, for example, service categories such as emergency,commercial, or non-commercial. The connectivity schedule can be adjustedto respond to a network condition, or a NB-IoT capability or service.The adjustment can include causing an NB-IoT device to connect to thenetwork less/more often and/or for shorter/longer time periods.

Another aspect of the technology relates to a virtual universalintegrated circuit card (UICC) that is integrated into an NB-IoT hostdevice. An example of a UICC is a SIM card, which providesauthentication and encryption functions for smartphones. However, aconventional SIM card is not reconfigurable, is external from its hostdevice, and consumes the same amount of host resources as any other SIMcard, which is particularly problematic for diverse, low-power NB-IoTdevices that could benefit from flexible authentication and encryptionthat is less resource intensive to operate. The technology allows anetwork to dynamically re/configure a virtual UICC, to optimize theavailability and utilization of host device resources. As such, thenetwork can determine and allocate an adequate amount of authenticationand encryption resources to perform UICC functions. The authenticationand encryption resources can be dynamically reset by the network basedon, for example, a network condition, NB-IoT device capability, NB-IoTdevice services, priorities, etc.

Another aspect of the technology is a dynamic NB-IoT key managementsystem that can provide keys of different encryption strengths fordifferent NB-IoT devices. Normally, an NB-IoT device must beauthenticated every time that it re/connects to a 5G network, whichinvolves a key exchange with the 5G network. A conventional networktypically generates the same types of keys with the same amount ofencryption security, which is problematic because 5G networks supportnumerous diverse, low-cost NB-IoT devices that do not all need the samelevel of encryption security. For example, NB-IoT devices that pose lesssecurity risks or are less critical can use an encryption key with alower encryption level strength that consumes less resources to generateand process.

The described technology thus improves NB-IoT devices. Additionalrelated features are described in the assignee's related applicationsincluding U.S. patent application Ser. No. ______, filed ______, titled“Configurable UICC Integrated in NB-IoT Device,” U.S. patent applicationSer. No. ______, filed ______, titled “Encryption Key Management forNB-IoT Devices,” U.S. patent application Ser. No. ______, filed ______,titled “Detecting Malicious Small Cells Based on a ConnectivitySchedule,” U.S. patent application Ser. No. ______, filed ______, titled“Detecting Malicious Small Cells Based on a Connectivity Schedule,” U.S.patent application Ser. No. 16/849,158, filed Apr. 15, 2020, titled“On-Demand Security Layer for a 5G Wireless Network,” and U.S. patentapplication Ser. No. 16/921,765, filed Jul. 6, 2020, titled “SecuritySystem for Managing 5G Network Traffic,” each of which are incorporatedby reference in their entireties for all purposes.

Wireless Communications System

FIG. 1 is a block diagram that illustrates a wireless communicationsystem 100 (“system 100”) in which aspects of the disclosed technologyare incorporated. The system 100 includes base stations 102-1 through102-4 (also referred to individually as “base station 102” orcollectively as “base stations 102”). A base station is a type ofnetwork access node (NAN) that can also be referred as a cell site, abase transceiver station, or a radio base station. The system 100 caninclude any combination of NANs including an access point, a radiotransceiver, a gNodeB (gNB), NodeB, eNodeB (eNB), Home NodeB, a HomeeNodeB, or the like. In addition to being a WWAN base station, a NAN canbe a WLAN access point, such as an IEEE 802.11 access point.

The NANs of a network formed by the system 100 also include wirelessdevices 104-1 through 104-8 (referred to individually as “wirelessdevice 104” or collectively as “wireless devices 104”) and a corenetwork 106. The wireless devices 104-1 through 104-8 are capable ofcommunication using various connectivity standards. For example, a 5Gcommunication channel can use mmW access frequencies of 28 GHz. In someimplementations, the wireless device 104 can operatively couple to abase station 102 over an LTE/LTE-A communication channel, which isreferred to as a 4G communication channel.

The core network 106 can provide, manage, or control security services,user authentication, access authorization, tracking, Internet Protocol(IP) connectivity, and other access, routing, or mobility functions. Thebase stations 102 interface with the core network 106 through a firstset of backhaul links 108 (e.g., S1) and can perform radio configurationand scheduling for communication with the wireless devices 104 or canoperate under the control of a base station controller (not shown). Insome examples, the base stations 102 can communicate, either directly orindirectly (e.g., through the core network 106), with each other over asecond set of backhaul links 110-1 through 110-3 (e.g., X1), which canbe wired or wireless communication links.

The base stations 102 can wirelessly communicate with the wirelessdevices 104 via one or more base station antennas. The cell sites canprovide communication coverage for geographic coverage areas 112-1through 112-4 (also referred to individually as “coverage area 112” orcollectively as “coverage areas 112”). The geographic coverage area 112for a base station 102 can be divided into sectors making up only aportion of the coverage area (not shown). The system 100 can includebase stations of different types (e.g., macro and/or small cell basestations). In some implementations, there can be overlapping geographiccoverage areas 112 for different service environments (e.g.,Internet-of-Things (IOT), mobile broadband (MBB), vehicle-to-everything(V2X), machine-to-machine (M2M), machine-to-everything (M2X),ultra-reliable low-latency communication (URLLC), machine-typecommunication (MTC)).

In some examples, the system 100 can include a 5G network and/or anLTE/LTE-A network. In an LTE/LTE-A network, the term eNB is used todescribe the base stations 102 and, in 5G or new radio (NR) networks,the term gNBs is used to describe the base stations 102 that include mmWcommunications. The system 100 can form a heterogeneous network in whichdifferent types of base stations provide coverage for variousgeographical regions. For example, each base station 102 can providecommunication coverage for a macro cell, a small cell, and/or othertypes of cells. As used herein, the term “cell” can relate to a basestation, a carrier or component carrier associated with the basestation, or a coverage area (e.g., sector) of a carrier or base station,depending on context.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and can allow unrestricted access bywireless devices with service subscriptions with the network provider.As indicated earlier, a small cell is a lower-powered base station, ascompared with a macro cell, and can operate in the same or different(e.g., licensed, unlicensed) frequency bands as macro cells. Examples ofsmall cells include pico cells, femto cells, and micro cells. Ingeneral, a pico cell can cover a relatively smaller geographic area andcan allow unrestricted access by wireless devices with servicesubscriptions with the network provider. A femto cell covers arelatively small geographic area (e.g., a home) and can providerestricted access by wireless devices having an association with thefemto cell (e.g., wireless devices in a closed subscriber group (CSG),wireless devices for users in the home). A base station can support oneor multiple (e.g., two, three, four, and the like) cells (e.g.,component carriers). All fixed transceivers noted herein that canprovide access to the network are NANs.

The communication networks that accommodate various disclosed examplescan be packet-based networks that operate according to a layeredprotocol stack. In the user plane, communications at the bearer orPacket Data Convergence Protocol (PDCP) layer can be IP-based. A RadioLink Control (RLC) layer then performs packet segmentation andreassembly to communicate over logical channels. A Medium Access Control(MAC) layer can perform priority handling and multiplexing of logicalchannels into transport channels. The MAC layer can also use Hybrid ARQ(HARQ) to provide retransmission at the MAC layer, to improve linkefficiency. In the control plane, the Radio Resource Control (RRC)protocol layer provides establishment, configuration, and maintenance ofan RRC connection between a wireless device 104 and the base stations102 or core network 106 supporting radio bearers for the user planedata. At the Physical (PHY) layer, the transport channels are mapped tophysical channels.

As illustrated, the wireless devices 104 are distributed throughout thesystem 100, where each wireless device 104 can be stationary or mobile.A wireless device can be referred to as a mobile station, a subscriberstation, a mobile unit, a subscriber unit, a wireless unit, a remoteunit, a handheld mobile device, a remote device, a mobile subscriberstation, an access terminal, a mobile terminal, a wireless terminal, aremote terminal, a handset, a mobile client, a client, or the like.Examples of a wireless device include user equipment (UE) such as amobile phone, a personal digital assistant (PDA), a wireless modem, ahandheld mobile device (e.g., wireless devices 104-1 and 104-2), atablet computer, a laptop computer (e.g., wireless device 104-3), awearable (e.g., wireless device 104-4). A wireless device can beincluded in another device such as, for example, a drone (e.g., wirelessdevice 104-5), a vehicle (e.g., wireless device 104-6), an augmentedreality/virtual reality (AR/VR) device such as a head-mounted displaydevice (e.g., wireless device 104-7), an IoT device such as an appliancein a home (e.g., wireless device 104-8), a NB-IoT device, or awirelessly connected sensor that provides data to a remote server over anetwork.

A wireless device can communicate with various types of base stationsand network equipment at the edge of a network including macroeNBs/gNBs, small cell eNBs/gNBs, relay base stations, and the like. Awireless device can also communicate with other wireless devices eitherwithin or outside the same coverage area of a base station viadevice-to-device (D2D) communications.

The communication links 114-1 through 114-11 (also referred toindividually as “communication link 114” or collectively as“communication links 114”) shown in system 100 include uplink (UL)transmissions from a wireless device 104 to a base station 102, and/ordownlink (DL) transmissions, from a base station 102 to a wirelessdevice 104. The downlink transmissions may also be called forward linktransmissions while the uplink transmissions may also be called reverselink transmissions. Each communication link 114 includes one or morecarriers, where each carrier can be a signal composed of multiplesub-carriers (e.g., waveform signals of different frequencies) modulatedaccording to the various radio technologies described above. Eachmodulated signal can be sent on a different sub-carrier and carrycontrol information (e.g., reference signals, control channels),overhead information, user data, etc. The communication links 114 cantransmit bidirectional communications using FDD (e.g., using pairedspectrum resources) or TDD operation (e.g., using unpaired spectrumresources). In some embodiments, the communication links 114 include LTEand/or mmW communication links.

In some embodiments of the system 100, the base stations 102 and/or thewireless devices 104 include multiple antennas for employing antennadiversity schemes to improve communication quality and reliabilitybetween base stations 102 and wireless devices 104. Additionally oralternatively, the base stations 102 and/or the wireless devices 104 canemploy multiple-input, multiple-output (MIMO) techniques that may takeadvantage of multi-path environments to transmit multiple spatial layerscarrying the same or different coded data.

In some embodiments, the wireless devices 104 are capable ofcommunicating signals via the LTE network and an mmW system (e.g., aspart of a 5G/NR system). Accordingly, the wireless device 104 cancommunicate with the base station 102 over an LTE link and/or with atransmission point (TP) or base station (BS) over an mmW link. Inanother example, at least one of the base stations 102 communicatessignals via the LTE network and the mmW system over one or morecommunication links 114. As such, a base station 116 may be referred toas an LTE+mmW eNB or gNB or as an LTE+mmW TP/BS/mmW-BS.

FIG. 2 is a block diagram that illustrates an architecture of networkfunctions 200 of a 5G network. An NB-IoT device 202 can access the 5Gnetwork via a RAN 204, through a NAN such as a small cell. In someimplementations, an NB-IoT device can be part of the RAN 204. Thearchitecture of the network functions 200 includes an authenticationserver function (AUSF) 216, a unified data management (UDM) 218, anaccess and mobility management function (AMF) 212, a policy controlfunction (PCF) 214, a session management function (SMF) 220, and a userplane function (UPF) 222. The PCF 214 can connect with one or moreapplication functions (AFs) 224. The UPF 222 can connect with one ormore data networks (DNs) 223. The interfaces N1 through N15 define thecommunications and/or protocols between each function or component, asdescribed in relevant standards. The UPF 222 is part of the user planeand the AMF 212, SMF 220, PCF 214, AUSF 216, and UDM 218 are part of thecontrol plane. The UPFs can be deployed separately from control planefunctions and the network functions of the control plane are modularizedsuch that they can be scaled independently.

A UDM introduces the concept of user data convergence (UDC) thatseparates the user data repository (UDR) storing and managing subscriberinformation from the frontend that processes the subscriber information.The UDM 218 is associated with a database (not shown) that can containprofile data for subscribers and/or other data that can be used toauthenticate network entities (e.g., subscribers, wireless devices).Given the large number of wireless devices (e.g., IoT devices) that canconnect to the 5G network, the UDM 220 contains a very large amount ofdata that is accessed by NANs and network functions to authenticatenetwork entities. This leads to high latency of control signaling, alongwith large numbers of queries across the network for the UDM.

Connectivity Scheduler for NB-IoT Devices

The disclosed technology includes a connectivity scheduler for NB-IoTdevices. Examples of the network node(s) include a combination of thenetwork nodes shown in FIG. 2. For example, a UDM function of a 5Gnetwork can manage the connectivity schedule, which can be implementedas access policies of a PCF. In particular, the UDM stores a deviceprofile for each NB-IoT, which includes capability and serviceinformation. The capability or service information can be obtained froman SMF or an IMS function. The device profiles can be used to prioritizeconnections based on, for example, service categories such as emergency,business, or leisure. Further, the connectivity schedule can be adjustedin response to changed network conditions or changed devicecapabilities. The adjustment can include connecting less/more oftenand/or for shorter/longer periods.

FIG. 3 is a flowchart that illustrates a method 300 performed by one ormore network nodes to update a connectivity schedule for intermittentconnectivity between NB-IoT devices and a wireless telecommunicationsnetwork (“network”). For example, the network node(s) can include a UDMnode that authorizes access to the network by the NB-IoT devices inaccordance with the connectivity schedule and a PCF including multipleaccess policies that implement the connectivity schedule. An example ofan NB-IoT device includes a wireless device with a processor, memory,power source, sensor, and a transceiver that can intermittently connectwith the network to report sensor data. The sensor data can beindicative of a temperature or image data captured by a camera enabledNB-IoT device. Hence, the NB-IoT device can intermittently connect tothe network to provide updated sensor data.

At 302, the network node(s) can maintain the connectivity schedule,which includes a device profile for each of multiple NB-IoT devices. Theconnectivity schedule can include entries for each NB-IoT device in adevice profile. The device profile can include device type, location,(e.g., GPS, country, state, city, region) and unique identifyinginformation such as a MAC address or IP address. The device profile canalso indicate a capability or communications service of the NB-IoT.

The network node(s) can obtain device-specific data indicative of acapability or service of an NB-IoT device from a SMF node or an IMS nodeof the network. The capability or service can be recorded in theschedule based on the device-specific data. Examples of the capabilityinclude total or remaining processor load capacity, memory capacity, andpower capacity (e.g., battery charge remaining). Examples of services(e.g., communications services) include an emergency service (e.g.,hospital, law enforcement, critical), a commercial service (e.g.,business, standard), and a non-commercial service (e.g., leisure,basic).

The connectivity schedule can categorize NB-IoT devices into groups ofpriority levels based on capabilities or services of the NB-IoT devices.The priority levels can be hierarchical to include high, medium, or lowpriority levels. Hence, the connectivity schedule can categorize NB-IoTdevices according to services that they individually or collectivelysupport. For example, the network node(s) can categorize NB-IoT devicesinto a high priority level for an emergency service, a medium prioritylevel for a commercial service, and a low priority level for anon-commercial service.

In one example, an NB-IoT device that is categorized in the highpriority level can be scheduled for connecting to the 5G network morefrequently or for a longer time period compared to any NB-IoT devicethat is categorized in a medium priority level, and another NB-IoTdevice that is categorized in the medium priority level is scheduled forconnecting to the network more frequently or for a longer time periodcompared to any NB-IoT device that is categorized in the low prioritylevel. In another example, the levels can include threat levels thatindicate the risk or threat to the network of a cybersecurity attack.For example, a hierarchy of threat levels can include high, medium, andlow risk or threat levels.

At 304, the network node(s) can cause the NB-IoT devices to connect tothe network in accordance with the connectivity schedule. In particular,the NB-IoT devices connect intermittently with different time patternsbased on the priority levels of the NB-IoT devices. The different timepatterns can include connecting to the network beginning at differentpoints in time or connecting for different time periods (e.g., timedurations). For example, five NB-IoT devices can be scheduled to connectto the network every hour for 15 minutes, where the beginning of anyconnection is offset from any other connection by 1 minute. In otherexample, the five NB-IoT devices are scheduled to connect to the networkevery hour for different time periods (e.g., 1, 2, 3, 4, or 5 minutes).In yet another example, the five NB-IoT devices can connectintermittently with the network based on combinations of different timeperiods beginning at different points in time.

In one example, a high priority NB-IoT device (e.g., supports emergencyservices) is schedule to connect before or for a longer period relativeto a medium-priority NB-IoT device (e.g., supports commercial services),which is scheduled to connect before or for a longer period relative toa low-priority NB-IoT device (e.g., supports non-commercial services).The schedule does not necessarily indicate fixed times to connect to thenetwork. Instead, the schedule can indicate a priority order for NB-IoTdevices to connect to the network when the network is available toestablish and/or maintain the connections. For example, when the networkhas a limited bandwidth, only high-priority NB-IoT devices can connectand, as more bandwidth becomes available, the medium-priority NB-IoTdevices are allowed to connect to the network before allowing thelow-priority NB-IoT devices to connect to the network. In anotherexample, the different time patterns are unique among priority levelssuch that any NB-IoT devices of a specific priority level connect to thenetwork at the same point in time or for the same time period.

At 306, the network node(s) detects a change in a condition of the 5Gnetwork based on a network activity. Examples include a change of anetwork load such as an increase or decrease in network traffic orquantity of devices connected to the network. This can occur, forexample, when there is a sports or political event in an area withNB-IoT devices such that the network gets overloaded with connectionrequests from other wireless devices in an area.

At 308, in response to a detected change in a current condition of thenetwork, the system can dynamically adjust the connectivity schedulesuch that at least some of the NB-IoT devices are scheduled to connectto the 5G network according to new time patterns different from theprevious time patterns. For example, when the network load increases,the connectivity schedule is adjusted to reduce the connectivity oflower priority NB-IoT devices and increase or maintain the connectivityof higher priority NB-IoT devices. Similarly, when the network loaddecreases, the connectivity schedule is adjusted to increase theconnectivity of lower priority NB-IoT devices.

The adjustments can occur per one or more (e.g., groups) of NB-IoTdevices. For example, the connectivity schedule can group NB-IoT devicesaccording to regions of the network. That is, the NB-IoT devices canbelong to different regional groups. The connectivity for one group canbe adjusted one way while the connectivity for a second group can beadjusted another way, in response to the same detected condition of thenetwork.

Configurable UICC Integrated in NB-IoT Device

The disclosed technology includes a Universal Integrated Circuit Card(UICC) that is integrated into an NB-IoT host device. An example of aUICC is a Subscriber/Services Identification/Identity Module (SIM) cardthat provides authentication and encryption for smartphones. Forexample, a UICC can securely store an International Mobile SubscriberIdentity (IMSI) and related cryptographic key used to identify andauthenticate a subscriber on a host device. The stored key informationcan include a unique serial number, security authentication andciphering information such as an authentication key (e.g., a 8-bit,64-bit, 128-bit, 128-bit, or 256-bit encryption keys), temporaryinformation related to a local network, which is received from a localcarrier, a list of services that a subscriber can access such as anoperator-specific emergency number, Short Message Service Center (SMSC)number, Service Provider Name (SPN), Service Dialing Number (SDN),advice-of-charge parameters, and Value Added Service (VAS) application.The UICC can also store passwords such as a Personal IdentificationNumber (PIN) and a Personal Unblocking Code (PUK) for PIN unlocking.

In operation, a conventional UICC identifies a subscriber and a wirelessoperator so that a network can identify the subscriber's service planand services. A UICC can store data about user contacts and enable acryptographically secure and reliable connection with the network. Insome instances, the UICC is the best and only universal applicationdelivery platform that works for mobile devices. The UICC ensures theintegrity and security of all kinds of personal data and it typicallyholds a few hundred kilobytes of data.

A UICC can store several applications. An example of an application isan IP Multimedia Services Identity Module (ISIM), which includes anApplication Dedicated File (ADF) that contains multiple Elementary Files(EFs). This module contains parameters for identifying andauthenticating the user to the IMS. The ISIM can include an IPMultimedia Private Identity (IMPI), a home operator domain name, one ormore IP Multimedia Public Identity (IMPU) and a long-term secret used toauthenticate and calculate cipher keys. The IMPU stored in the ISIM canbe used in emergency registration requests. The authentication and keyagreement mechanism are typically run by the IMSI is required forservices in the IMS.

A typical UICC (e.g., SIM card) is not physically integrated into a hostdevice and is not remotely configurable. Further, a conventional UICCconsumes the same amount of host resources regardless of the hostdevice, which is problematic in the context of diverse, low-power NB-IoTdevices that could benefit from flexible authentication and encryptionfunctions, which could be part of an application or service that arebroadly referred to herein as “resources.” Hence, existing UICCtechnology treats NB-IoT devices the same way, which is inefficientgiven the diversity of the NB-IoT devices and their varying needs forauthentication and encryption. For example, an NB-IoT device thatregularly supports high volumes of network traffic and has a high riskof being hacked should implement one or more robust authentication andencryption functions. On the other hand, another NB-IoT device thatrarely communicates with the network, is in a geographically secure area(e.g., unreachable by bad actors), and has limited services run by abattery with a limited capacity could run more efficiently with arelatively weaker authentication and encryption service.

An embedded-SIM (eSIM) or embedded universal integrated circuit card(eUICC) is a form of programmable SIM card that is embedded directlyinto a device. In machine to machine (M2M) applications, where there isno requirement to change the SIM card, this avoids the requirement for aconnector, which improves reliability and security. An eSIM can beprovisioned remotely and end-users can add or remove operators withoutthe need to physically swap a SIM from the device. However, an eSIM isnot dynamic; instead, a fixed set of resources of a host device areassigned for the eSIM.

The disclosed technology includes a UICC (also referred to herein as avirtual UICC) that is physically integrated into a host device to thwarthacking and enable remote re/configuring by the network to efficientlyutilize NB-IoT device resources. As such, the network can determine andcontrol an allocation of authentication and encryption resources toperform a necessary scope of UICC authentication and encryptionfunctions. The authentication and encryption resources can bedynamically reset by a network node based on, for example, currentnetwork conditions, device capabilities, communications services,priorities, etc.

FIG. 4 is a flowchart that illustrates a method performed by one or morenetwork nodes to configure a virtual UICC in an NB-IoT device. Examplesof the network node(s) include a combination of the network nodes shownin FIG. 2.

At 402, the network node(s) maintain a device profile that indicates acapability and a communications service of an NB-IoT device. Examples ofcapabilities include a storage, power, or process utilization orcapacity (e.g., battery life). Examples of communications servicesinclude an emergency service, a commercial service, and a non-commercialservice. The emergency service can include security, healthcare, or lawenforcement communications that are supported by the NB-IoT device. Forexample, an NB-IoT device that generates data of a hospital can bedesigned for emergency services. Examples of the commercial serviceinclude any communications service for business operations, andnon-commercial service can include ordinary or leisure communicationsservices. The commercial service can be designated as part of a serviceplan for businesses while the non-commercial service can be a defaultbasic service.

At 404, the network node(s) determines one or more authentication andencryption functions for the UICC of the NB-IoT devices. Theauthentication and encryption functions can be required to support thecommunication service of the NB-IoT device based on the capability ofthe NB-IoT device and a condition of the network. In one example, theNB-IoT device is categorized in one of multiple categories that are eachassociated with a categorical authentication and encryption function.Then, the authentication and encryption functions can be set to includethe categorical authentication and encryption functions. In anotherexample, the network node(s) designate a priority level for the NB-IoTdevice and the authentication and encryption functions are set based inpart on a priority level of an NB-IoT device. The priority levels can behierarchical to include high, medium, and/or low priority levels. Apriority level can be set based on a type of communication service thatit supported by a particular NB-IoT device. In another example, thelevels can include threat levels that indicate the risk or threat to thenetwork of a cybersecurity attack. For example, a hierarchy of threatlevels can include high, medium, and low risk or threat levels.

At 406, the network node(s) configure the virtual UICC to allocateauthentication and encryption functions of the NB-IoT device. Thenetwork node(s) can communicate a command over the network to cause theNB-IoT device to adjust an allocation of an authentication andencryption function of a UICC. For example, the network nodes can changean encryption strength of a cypher key employed by the NB-IoT device.That is, the authentication and encryption functions associated with aUICC, as described earlier, can be adjusted remotely from the networkbased on the state of the NB-IoT device and a current network condition,which ensures flexibility to dynamically adjust to a change or toprovide a suitable degree of authentication and encryption services whenneeded, and not more than necessary.

At 408, the network node(s) detect one or more change(s) of thecondition of the network, the capability of the NB-IoT device, or acommunications service supported by the NB-IoT device. A changedcondition can include a changed load of the network based on a quantityof devices connected to the network or an amount of network trafficcommunicated on the network. In another example, the changed conditioncan include the addition of a network access node such as a base stationor addition of a second NB-IoT device that can be used to offloadcommunications from the first NB-IoT device. An example of a changedcapability includes a changed storage capacity or a power capacity(e.g., remaining battery) of the NB-IoT device.

At 410, in response to the detected change, the network node(s)determine one or more updated authentication and encryption functionsfor the UICC of the NB-IoT device. For example, an NB-IoT can have adefault non-commercial service, which can be changed remotely to acommercial service. The change to the commercial service can beaccompanied to a change in an authentication or encryption function ofthe NB-IoT device. In another example, the network node(s) can determinethat an NB-IoT device changed to support an emergency service and,switch an authentication or encryption function of the NB-IoT device formore robust security. In yet another example, a changed condition canalso relate to the same service (e.g., emergency, business, leisure) atdifferent threat levels (e.g., high, medium, low) to the network. Forexample, the network nodes(s) can adapt a connectivity schedule toprovide a higher degree of encryption and lower connectivity when thenetwork node(s) detect an increased threat to the network from an NB-IoTdevice, related communications, or service. Thus, the authentication andencryption functions are updated to support services based on acondition of the network (including a security threat), a capability ofthe NB-IoT device, or a service of the NB-IoT device.

At 412, the network node(s) dynamically reconfigures the virtual UICC tosupport the second authentication and encryption functions for the UICCof the NB-IoT device. In one example, the second authentication andencryption functions are more robust relative to prior authenticationand encryption functions, and the UICC is reconfigured for the secondauthentication and encryption functions when a network conditionchanges, such as an environment where the NB-IoT device primarilysupports a commercial service and where the network load has increased.Likewise, the new authentication and encryption functions can be weakerwhen a network load is consistently lower. In another example, adetected change in the battery capacity of the NB-IoT device can causethe network node(s) to dynamically reconfigure the NB-IoT for weakerauthentication and encryption functions that consume less energy. In yetanother example, the current authentication and encryption functions arechanged to support a new service that demands increased complexity orutilization of host device resources. Conversely, authentication andencryption functions can be reset lower when a complexity or utilizationof the service decreases.

Key Management system for NB-IoT Devices

The disclosed technology includes a NB-IoT key management system thatcan dynamically provide keys of different encryption strengths to NB-IoTdevices. Normally, an NB-IoT device must be authenticated every timethat it connects or reconnects to a telecommunications network (e.g., 5Gnetwork). The authentication process involves a key exchange between theNB-IoT device and a network node. Further, a conventional networkgenerates encryption keys with the same level of encryption strength.This conventional technique provides a baseline threshold amount ofsecurity for a network. However, the same technique applied to NB-IoTdevices is problematic because, for example, 5G networks supportnumerous diverse and low-cost NB-IoT devices that do not all need thesame baseline level of encryption strength to secure all the device andits communications the same way. For example, NB-IoT devices that poseless security risks or are less critical can use an encryption key witha lower encryption strength that is less computationally burdensome togenerate and process by the NB-IoT device and the network. Doing soimproves the efficiency of the network and the NB-IoT device, whichcould have limited computational and energy resources.

The encryption keys can range in strength from high (e.g., robust)encryption strength to low (e.g., weak) encryption strength. The networknode(s) can generate and distribute a finite number of each type of key.For example, the network node(s) can generate a greater quantity of8-bit encryption keys compared to a quantity of 64-bit encryption keys.The 8-bit encryption keys are less burdensome to process (e.g.,decipher) by the NB-IoT device and the network such that distributingencryption keys with lower encryption strengths is favored, where doingso does not unduly risk the security of the network. The network candynamically adjust the encryption strength of an encryption key for anNB-IoT device to accommodate and/or adapt to a changing network orchanges to the NB-IoT devices.

FIG. 5 is a flowchart that illustrates a method 500 performed by networknode(s) to dynamically manage (e.g., generate, distribute, and update)encryption keys of varying encryption strengths for NB-IoT devices of awireless telecommunications network. Examples of the network node(s)include any combination of the nodes shown in FIG. 2.

At 502, the network node(s) maintain a database that stores a deviceprofile for each NB-IoT device. A device profile indicates a capabilityor a communications service of an NB-IoT device. Examples ofcapabilities include storage, power, or processor capabilities includingcapacities and utilization. In one example, a capability includes asecurity profile where an encryption key strength is proportional to thesecurity profile. Hence, the profile indicates a degree of securityrequired by the NB-IoT device

Examples of the communications service include an emergency service, acommercial service, and a non-commercial service. The emergency servicecan include security, healthcare, or law enforcement communications thatare supported by the NB-IoT device. For example, an NB-IoT device thatis physically located by a hospital can be designed for emergencyservices. Examples of a commercial service include a service forbusiness operations, and non-commercial service can include basic orleisure services. The commercial service can be designated as part of asubscriber plan for businesses while the non-commercial service can be adefault basic service for subscribers. In some instances, an NB-IoTdevice is classified or categorized into priority levels based on thedevice capability or the communications service of the NB-IoT device.Examples of a hierarchical priority levels include high, medium, and lowpriority levels. The priority levels can be set based on the type ofcommunications services that are supported by the NB-IoT device. TheNB-IoT devices can be categorized into one or more of the prioritylevels based on the communications service of the NB-IoT device.

At 504, the network node(s) obtain multiple encryption keys for theNB-IoT devices. The encryption keys are associated with differentencryption strengths. Examples include a high encryption strength key, amoderate encryption strength key, a low encryption strength key, and anultra-low encryption strength key. In one example, the high encryptionstrength key is a 256-bit encryption key, the moderate encryptionstrength key is a 128-bit encryption key, the low encryption strengthkey is a 64-bit encryption key, and the ultra-low encryption strengthkey is an 8-bit encryption key. The encryption and decryption processingfor stronger encryption keys is more secure but is also resourceintensive compared to weaker encryption keys. Hence, using encryptionkeys can improve the efficiency of individual NB-IoT devices and thenetwork as a whole.

The network node(s) can generate a finite number of each type ofencryption key based in part on a current condition of the 5G network.The current condition of the network can include, for example, aquantity or type of wireless devices being supported by the network.Another example includes the current or statistical average networktraffic on the network. Further, the encryption keys can be generatedalgorithmically based on a condition of the network and/or valuesassociated with the NB-IoT devices such as locations, etc.

In 506, the network node(s) allocate encryption keys to NB-IoT devices.The network node(s) thus enable authentication of the NB-IoT devices inaccordance with key exchange processes between the multiple NB-IoTdevices and the network by using the encryption keys of differentencryption strengths. Further, the encryption keys can be used as acypher to encrypt/decrypt the communications of the NB-IoT devices, insome implementations.

The network node(s) can distribute the encryption keys to the NB-IoTdevices based on communication services of the NB-IoT devices and inaccordance with a normal (e.g., default) distribution scheme. In thedefault distribution scheme, the encryption keys are distributed byallocating lower strength encryption keys before allocating higherstrength encryption keys, where possible, balanced against the securityneeds of the network. In particular, the network node(s) distributes lowencryption strength keys after any ultra-low encryption strength keys,distributes moderate encryption strength keys after low encryptionstrength keys, and distributes high encryption strength keys aftermoderate encryption strength keys. The network node(s) can distribute ahigh encryption strength key despite readily available lower encryptionstrength keys when an NB-IoT device provides an emergency service orwhen the NB-IoT has a greater risk of being hacked (e.g., is physicallyaccessible to a bad actor).

The encryption keys for NB-IoT devices can be selected from finite setsof different encryption keys. That is, the available encryption keys caninclude a limited number of encryption keys in each of the different keysizes. As such, a first encryption key of a first encryption strength isallocated for a first NB-IoT device based on a first capability or afirst communication service of the first NB-IoT device. A secondencryption key of a second encryption strength is allocated for a secondNB-IoT device based on a second capability or a second communicationservice of the second NB-IoT device, and so on. In one example, a highencryption strength key is allocated for an NB-IoT device that supportsa high security risk service, a moderate encryption strength key isallocated for an NB-IoT device that supports a moderate security riskservice, a low encryption strength key is allocated for an NB-IoT devicethat supports a low security risk service, and an ultra-low encryptionstrength key is allocated for an NB-IoT device that supports anultra-low security risk service.

At 508, the network node(s) detect a change in a condition of thenetwork or a change in a capability or a communications service of theNB-IoT device. A changed condition can include a changed load of thenetwork based on a current quantity of devices connected to the networkor volume of network traffic on the network. In another example, thechanged condition can include the addition of a network access node suchas a base station or addition of a second NB-IoT device that can be usedto offload communications of the first NB-IoT device. An example of achanged capability includes a changed storage capacity or changed powercapacity (e.g., remaining battery) of the NB-IoT device.

At 510, in response to the detected change, the network node(s) refresha first NB-IoT device with a second encryption key of a secondencryption strength different from the first encryption key of the firstencryption strength. For example, refreshing the first NB-IoT devicewith the second encryption key can include replacing the firstencryption key with the second encryption key or updating the firstencryption key with the second encryption key (e.g., increase theencryption strength without replacing the key).

In an example, the network node(s) detect an increased load on thenetwork and, in response, refresh the encryption keys of at least someof the NB-IoT devices in accordance with a high load allocation schemewhere higher encryption strength keys are replaced with lower encryptionstrength keys. In another example, the network node(s) detect adecreased load on the network and, in response, refresh the encryptionkeys of at least some of the NB-IoT devices in accordance with a lowload allocation scheme where lower encryption strength keys are replacedwith higher encryption strength keys.

Although the disclosed technology is described in the context ofencryption keys of varying encryption strengths, implementations includeother types of security features or forms of authentication. Forexample, the network node(s) can distribute any combination of differenttypes of security features including encryption algorithms,error-detecting codes (e.g., cyclic redundancy check (CRC), hashing dataintegrity check), in addition or alternative to encryption keys. Hence,the network node(s) can cause the NB-IoT devices to employ differentencryption algorithms, error-detecting codes, and/or encryption keys inresponse to a detected change as described earlier. For example,error-detecting codes can be initially distributed and, upon detectionof an increased security threat to the network, the network node(s) caninstantiate encryption algorithms or distribute keys for at least someof the NB-IoT devices that pose a greater threat to the network.

Computer System

FIG. 6 is a block diagram that illustrates an example of a computersystem 600 in which at least some operations described herein can beimplemented. For example, components discussed in FIGS. 1-5 can includeor host components of the computing system 600.

As shown, the computer system 600 can include one or more processors602, main memory 606, non-volatile memory 610, a network interfacedevice 612, video display device 618, an input/output device 620, acontrol device 622 (e.g., keyboard and point device), a drive unit 624that includes a storage medium 626, and a signal generation device 630that are communicatively connected to a bus 616. The bus 616 representsone or more physical buses and/or point-to-point connections that areconnected by appropriate bridges, adapters, or controllers. The bus 616therefore can include a system bus, a Peripheral Component Interconnect(PCI) bus or PCI-Express bus, a HyperTransport or industry standardarchitecture (ISA) bus, a small computer system interface (SCSI) bus, auniversal serial bus (USB), IIC (I2C) bus, or an Institute of Electricaland Electronics Engineers (IEEE) standard 1394 bus (also referred to as“Firewire”). Various common components (e.g., cache memory) are omittedfrom FIG. 6 for brevity. Instead, the computer system 600 is intended toillustrate a hardware device on which components illustrated ordescribed relative to the examples of FIGS. 1-5 and any other componentsdescribed in this specification can be implemented.

The computer system 600 can take any suitable physical form. Forexample, the computing system 600 may share a similar architecture asthat of a personal computer (PC), tablet computer, mobile telephone,game console, music player, wearable electronic device,network-connected (“smart”) device (e.g., a television or home assistantdevice), AR/VR systems (e.g., head-mounted display), or any electronicdevice capable of executing a set of instructions that specify action(s)to be taken by the computing system 600. In some embodiment, thecomputer system 600 can be an embedded computer system, a system-on-chip(SOC), a single-board computer system (SBC) or a distributed system suchas a mesh of computer systems or include one or more cloud components inone or more networks. Where appropriate, one or more computer systems600 can perform operations in real-time, near real-time, or in batchmode.

The processor 602 can be, for example, a central processing unit, aconventional microprocessor (e.g., Intel Pentium processor). The memory(e.g., main memory 606, non-volatile memory 610, machine-readable medium626) can be local, remote, or distributed. Although shown as singlemedium, the machine-readable medium 626 can include multiple media(e.g., a centralized/distributed database and/or associated caches andservers) that store one or more sets of instructions 628. Themachine-readable (storage) medium 626 can include any medium that iscapable of storing, encoding, or carrying a set of instructions forexecution by the computing system 600. One of skill in the relevant artwill recognize that the machine-readable medium 626 can include any typeof medium that is accessible by the processor. The machine-readablemedium 626 can be non-transitory or comprise a non-transitory device. Inthis context, a non-transitory storage medium can include a device thatis tangible, meaning that the device has a concrete physical form,although the device can change its physical state. Thus, for example,non-transitory refers to a device remaining tangible despite this changein state.

In general, the routines executed to implement the embodiments of thedisclosure may be implemented as part of an operating system or aspecific application, component, program, object, module, or sequence ofinstructions (collectively referred to as “computer programs”). Thecomputer programs typically comprise one or more instructions (e.g.,instructions 604, 608, 628) set at various times in various memory andstorage devices in computing device(s). When read and executed by theprocessor 602, the instruction(s) cause the computing system 600 toperform operations to execute elements involving the various aspects ofthe disclosure.

Although embodiments have been described in the context of fullyfunctioning computing devices, the various embodiments are capable ofbeing distributed as a program product in a variety of forms. Examplesof machine-readable storage media, machine-readable media, orcomputer-readable media include recordable-type media such as volatileand the non-volatile memory devices 610, removable flash memory, harddisk drives, optical disks, and transmission-type media such as digitaland analog communication links.

Software is typically stored in the non-volatile memory and/or the driveunit 624. When software is moved to the memory for execution, theprocessor 602 will typically make use of hardware registers to storevalues associated with the software, and local cache that, ideally,serves to speed up execution. As used herein, a software program isassumed to be stored at any known or convenient location (e.g.,non-volatile storage, hardware registers) when the software program isreferred to as “implemented in a computer-readable medium.” A processorcan be “configured to execute a program” when at least one valueassociated with the program is stored in a register readable by theprocessor.

The network interface device 612 enables the computing system 600 tomediate data in a network 614 with an entity that is external to thecomputing system 600 through any communication protocol supported by thecomputing system 600 and the external entity. Examiner of the networkinterface device 612 include a network adaptor card, a wireless networkinterface card, a router, an access point, a wireless router, a switch,a multilayer switch, a protocol converter, a gateway, a bridge, bridgerouter, a hub, a digital media receiver, and/or a repeater.

Further, the interface device 612 can include a firewall that governsand/or manages permission to access/proxy data in a computer network andtracks varying levels of trust between different machines and/orapplications. The firewall can be any number of modules having anycombination of hardware and/or software components able to enforce apredetermined set of access rights between a particular set of machinesand applications, machines and machines, and/or applications andapplications (e.g., to regulate the flow of traffic and resource sharingbetween these entities). The firewall may additionally manage and/orhave access to an access control list that details permissions includingthe access and operation rights of an object by an individual, amachine, and/or an application, and the circumstances under which thepermission rights stand.

Examples of the I/O devices 620 include a keyboard, a mouse or otherpointing device, disk drives, printers, a scanner, and other inputand/or output devices, including a display device. Examples of thedisplay device 618 can include a cathode ray tube (CRT), liquid crystaldisplay (LCD), or any display device.

In operation, the computer system 600 can be controlled by operatingsystem software that includes a file management system, such as a diskoperating system. One example of operating system software withassociated item management system software is the family of operatingsystems known as Windows® from Microsoft Corporation of Redmond, Wash.,and their associated item management systems. Another example ofoperating system software with its associated item management systemsoftware is the Linux™ operating system and its associated itemmanagement system. The item management system is typically stored in thenon-volatile memory and/or drive unit and causes the processor toexecute the various acts required by the operating system to input andoutput data and to store data in the memory, including storing items onthe non-volatile memory and/or drive unit.

The techniques introduced here can be implemented by programmablecircuitry (e.g., one or more microprocessors), software and/or firmware,special-purpose hardwired (i.e., non-programmable) circuitry, or acombination of such forms. Special-purpose circuitry can be in the formof one or more application-specific integrated circuits (ASICs),programmable logic devices (PLDs), field-programmable gate arrays(FPGAs), etc.

Some portions of the detailed description can be presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm can refer to aself-consistent sequence of operations leading to a desired result. Theoperations are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the following discussion,it is appreciated that throughout the description, discussions utilizingterms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or “generating” or the like, refer to theaction and processes of a computer system, or similar electroniccomputing device, that manipulates and transforms data represented asphysical (electronic) quantities within the computer system's registersand memories into other data similarly represented as physicalquantities within the computer system memories or registers or othersuch information storage, transmission or display devices.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems can be used with programs in accordance with the teachingsherein, or it can prove convenient to construct more specializedapparatus to perform the methods of some embodiments. The requiredstructure for a variety of these systems will appear from thedescription below. In addition, the techniques are not described withreference to any particular programming language, and variousembodiments can thus be implemented using a variety of programminglanguages.

In some circumstances, operation of a memory device, such as a change instate from a binary one to a binary zero or vice-versa, for example, cancomprise a transformation, such as a physical transformation. Withparticular types of memory devices, such a physical transformation cancomprise a physical transformation of an article to a different state orthing. For example, but without limitation, for some types of memorydevices, a change in state can involve an accumulation and storage ofcharge or a release of stored charge. Likewise, in other memory devices,a change of state can comprise a physical change or transformation inmagnetic orientation or a physical change or transformation in molecularstructure, such as from crystalline to amorphous or vice versa. Theforegoing is not intended to be an exhaustive list in which a change instate for a binary one to a binary zero or vice-versa in a memory devicecan comprise a transformation, such as a physical transformation.Rather, the foregoing is intended as illustrative examples.

REMARKS

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof means any connection or coupling,either direct or indirect, between two or more elements; the coupling orconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import can refer to this application as a whole andnot to any particular portions of this application. Where the contextpermits, words in the above Detailed Description using the singular orplural number may also include the plural or singular numberrespectively. The word “or” in reference to a list of two or more itemscovers all of the following interpretations of the word: any of theitems in the list, all of the items in the list, and any combination ofthe items in the list.

While specific examples of technology are described above forillustrative purposes, various equivalent modifications are possiblewithin the scope of the invention, as those skilled in the relevant artwill recognize. For example, while processes or blocks are presented ina given order, alternative implementations may perform routines havingsteps, or employ systems having blocks, in a different order, and someprocesses or blocks may be deleted, moved, added, subdivided, combined,and/or modified to provide alternative or sub-combinations. Each ofthese processes or blocks may be implemented in a variety of differentways. Also, while processes or blocks are at times shown as beingperformed in series, these processes or blocks may instead be performedor implemented in parallel, or may be performed at different times.Further, any specific numbers noted herein are only examples such thatalternative implementations can employ differing values or ranges.

Details of the disclosed embodiments may vary considerably in specificimplementations while still being encompassed by the disclosedteachings. As noted above, particular terminology used when describingcertain features or aspects of the invention should not be taken toimply that the terminology is being redefined herein to be restricted toany specific characteristics, features, or aspects of the invention withwhich that terminology is associated. In general, the terms used in thefollowing claims should not be construed to limit the invention to thespecific examples disclosed in the specification, unless the aboveDetailed Description explicitly defines such terms. Accordingly, theactual scope of the invention encompasses not only the disclosedexamples, but also all equivalent ways of practicing or implementing theinvention under the claims. Some alternative implementations can includeadditional elements to those implementations described above or includefewer elements.

Any patents and applications and other references noted above, and anythat may be listed in accompanying filing papers, are incorporatedherein by reference in their entireties, except for any subject matterdisclaimers or disavowals, and except to the extent that theincorporated material is inconsistent with the express disclosureherein, in which case the language in this disclosure controls. Aspectsof the invention can be modified to employ the systems, functions, andconcepts of the various references described above to provide yetfurther implementations of the invention.

To reduce the number of claims, certain embodiments are presented belowin certain claim forms, but the applicant contemplates various aspectsof an invention in other forms. For example, aspects of a claim can berecited in a means-plus-function form or in other forms, such as beingembodied in a computer-readable medium. A claim intended to beinterpreted as a mean-plus-function claim will begin with the words“means for.” However, the use of the term “for” in any other context isnot intended to invoke a similar interpretation. The applicant reservesthe right to pursue such additional claim forms in either thisapplication or in a continuing application.

I/We claim:
 1. A method performed by one or more network nodes formanaging connectivity between multiple narrowband Internet-of-Things(NB-IoT) devices and a 5G network, the method comprising: maintaining aconnectivity schedule that includes a device profile for each ofmultiple NB-IoT devices, wherein each device profile indicates acapability or a service of a respective NB-IoT device, and wherein theconnectivity schedule categorizes each of the multiple NB-IoT devicesinto one of multiple priority levels based on the capability or theservice of the NB-IoT device; causing the multiple NB-IoT devices toconnect to the 5G network in accordance with the connectivity schedule,wherein the multiple NB-IoT devices are caused to connect to the 5Gnetwork at different time patterns based on the multiple priority levelsof the multiple NB-IoT devices, and wherein the different time patternsinclude a particular time pattern for a particular NB-IoT device;detecting a change in a condition of the 5G network based on networkactivity; and in response to the detected change in the condition of the5G network, adjusting the connectivity schedule for the particularNB-IoT device to connect to the 5G network in accordance with a new timepattern different from the particular time pattern.
 2. The method ofclaim 1, wherein maintaining the connectivity schedule comprises:obtaining device-specific data of each NB-IoT device from a sessionmanagement function (SMF) or an IP multimedia subsystem (IMS) function;updating the capability or service for the connectivity schedule basedon the obtained device-specific data of the particular NB-IoT device;and categorizing each NB-IoT device into a high priority level for anemergency service, a medium priority level for a commercial service, anda low priority level for a non-commercial service, wherein a firstNB-IoT device that is categorized in the high priority level isscheduled for connecting to the 5G network more frequently or for alonger time period compared to any NB-IoT device that is categorized inthe medium priority level, and wherein a second NB-IoT device that iscategorized in the medium priority level is scheduled for connecting tothe 5G network more frequently or for a longer time period compared toany NB-IoT device that is categorized in the low priority level.
 3. Themethod of claim 1, wherein the different time patterns include differentpoints in time or different time periods for connecting the multipleNB-IoT devices with the 5G network.
 4. The method of claim 1, whereinthe one or more network nodes includes a unified data management (UDM)node that authorizes access to the 5G network for the multiple NB-IoTdevices in accordance with the connectivity schedule and a policycontrol function (PCF) including multiple access policies that implementthe connectivity schedule.
 5. The method of claim 1, wherein adjustingthe connectivity schedule comprises: decreasing connectivity of lowerpriority NB-IoT devices when a network load increases; and increasingconnectivity of lower priority NB-IoT devices when a network loaddecreases.
 6. The method of claim 1, wherein the connectivity schedulegroups NB-IoT devices per regions of the 5G network, and wherein themultiple NB-IoT devices belong to a first group, the method furthercomprising: adjusting the connectivity for the first group in accordancewith a first adjustment; and adjusting the connectivity for a secondgroup of NB-IoT devices in accordance with a second adjustment differentfrom the first adjustment.
 7. The method of claim 1, wherein thecapability includes an available load capacity and an available powercapacity such that each NB-IoT device is categorized into one of themultiple priority levels based on the capability of the NB-IoT device.8. The method of claim 1, wherein the service includes one of anemergency service, a commercial service, and a non-commercial service,and wherein each NB-IoT device is categorized into one of the multiplepriority levels based on the service of a respective NB-IoT device. 9.The method of claim 1, wherein the particular NB-IoT device is caused toconnect intermittently with the 5G network to report data generated by asensor of the particular NB-IoT device.
 10. The method of claim 1,wherein the different time patterns are unique between the multiplepriority levels such that NB-IoT devices of each priority level connectto the 5G network at a common point in time or during a common timeperiod.
 11. At least one non-transitory computer-readable storage mediumstoring connectivity data for a narrowband Internet-of-Things (NB-IoT)device of a wireless network and storing instructions to be executed byat least one processor, wherein execution of the instructions causeNB-IoT of a wireless network to: associate the multiple NB-IoT devicewith a priority level of a hierarchy of priority levels; cause theNB-IoT device to intermittently connect to the wireless network inaccordance with a connectivity schedule, wherein the NB-IoT device iscaused to connect to the wireless network at unique times among multipleNB-IoT devices of the wireless network in accordance with the prioritylevel; and dynamically adjust the connectivity schedule based on acurrent condition of the wireless network.
 12. The computer-readablestorage medium of claim 11 further causing the NB-IoT device to, priorto adjusting the connectivity schedule: receive an indication of adetect a change in a load of the wireless network, wherein an increasednetwork load causes a change in the connectivity schedule to reduceconnectivity by the NB-IoT device, and wherein a decreased network loadcauses a change in the connectivity schedule to increase connectivity bythe NB-IoT device.
 13. The computer-readable storage medium of claim 11,wherein the hierarchy of priority levels includes a high priority levelassociated with a critical service, a medium priority associated with astandard service, and a low priority level associated with a basicservice for the multiple NB-IoT devices.
 14. The computer-readablestorage medium of claim 11, wherein the hierarchy of priority levels ahigh priority level for an emergency service, a medium priority categoryfor a commercial service, and a low priority level for a non-commercialservice.
 15. The computer-readable storage medium of claim 11, whereinthe connectivity schedule is based on a security profile of the NB-IoTdevice, and wherein the security profile is indicative of either a high,medium, or low threat to the network by the NB-IoT device.
 16. A systemof a wireless telecommunications network, the system comprising: apolicy control function (PCF) node configured to: store multiple networkaccess policies as a connectivity schedule for multiple narrowbandInternet-of-Things (NB-IoT) devices, wherein the connectivity schedulecategorizes the multiple NB-IoT devices into one of multiple risk levelsassociated with time patterns in which the multiple NB-IoT devices arescheduled to connect to the wireless telecommunications network; and aunified data management (UDM) node configured to: enable the multipleNB-IoT devices to connect to the wireless telecommunications network inaccordance with the connectivity schedule; receive an indication of acondition of the wireless telecommunications network based on networkactivity; and cause the PCF node to adjust the connectivity schedulebased on the condition of the wireless telecommunications network andthe multiple risk levels.
 17. The system of claim 16 further comprising:a session management function (SMF) node configured to: obtaindevice-specific data of the multiple NB-IoT devices, wherein the devicespecific data includes capability data or service data for the multipleNB-IoT devices; and provide the device-specific data for the PCF node togenerate the connectivity schedule based in part on capability data orservice data included in the device-specific data.
 18. The system ofclaim 16 further comprising: an IP multimedia subsystem (IMS) nodeconfigured to: obtain device-specific data of the multiple NB-IoTdevices, wherein the device specific data includes capability data orservice data for the multiple NB-IoT devices; and provide thedevice-specific data for the PCF node to generate the connectivityschedule based in part on capability data or service data included inthe device-specific data.
 19. The system of claim 16, wherein the UDMnode is configured to enable the multiple NB-IoT devices to connect tothe wireless telecommunications network by authenticating each NB-IoTdevice in accordance with the connectivity schedule.
 20. The system ofclaim 16, wherein the condition includes a load of devices connected tothe wireless telecommunications network or a load of network trafficcommunicated over the wireless telecommunications network.